@dashrender said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@jaredbusch said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@msff-amman-itofficer said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@jaredbusch said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@msff-amman-itofficer said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@jaredbusch said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@msff-amman-itofficer said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@tim_g
@tim_g said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
@msff-amman-itofficer said in How Many Windows Server VMs Can You Run on Hyper-V SAMIT Video:
Oh and they provide the hyper v integration as cab file (guest agent):
windows6.x-hypervintegrationservices-x64.cab
I cant belive I complained when VIRT IO Tools was repackaged some time ago and they changed some folders in there ISO image, while MS gives you a .cab file and not even an executable.What do you mean? What VM are you trying to install? You shouldn't need any integration tools at all for any modern operating system on a VM. They come built in and are updated via Windows Update (if running Windows OS)
If you install RHEL or CentOS, you can download a Linux Integration Services .ISO if you need to. You simply run the ./install.sh file. All other modern Linux OSs already have the Hyper-V Integration built in to the kernel.
This is what i am talking about:
https://support.microsoft.com/en-US/help/3063109/hyper-v-integration-components-update-for-windows-virtual-machinesMethod 2: Microsoft Download Center
The following files are available for download from the Microsoft Download Center.
Operating system Update
All supported x86-based versions of Windows 8.1 Download Download the package now.
All supported x64-based versions of Windows 8.1 Download Download the package now.
All supported x64-based versions of Windows Server 2012 R2 Download Download the package now.
All supported x64-based versions of Windows Server 2012 Download Download the package now.
All supported x86-based versions of Windows 7 Download Download the package now.
All supported x64-based versions of Windows 7 Download Download the package now.
All supported x64-based versions of Windows Server 2008 R2 Download Download the package now.Go to the download, and it is all .cab files.
WTF are you talking about. This is not DVD media. You are doing it wrong from the beginning.
Ofcourse I know this is not DVD media, those are the Hyper-V agents that MS wants you to install on your guest machine, MS calls them Hyper-V integration components.
ESXi and KVM Virt IO all provides much better ways to get this installed on your guest machines, and dont provide you a dumb .cab file.
Just because you are not capable of providing a share to get access the files from within the VM does not mean the process is stupid.
Who wants to mount ISO files from the hypervisor all the time just to update software in a guest VM? That is the stupid thing.
Okay, granted what are the commands to create share in Windows hyper-V standalone? I tried and failed, or the only way to do so is to have share outside hyper-V like NAS ? if so both KVM and ESXi can be easier in sending files directly to the host.
I dont want to go to fight about who is the best Virtualization platform cause that is pointless, but my trial wit Hyper-V is everything required 2 extra steps to get it configured. While the competition it can be done with one step.
Why are you trying to put these files on the hypervisor? They have no need to be on the hypervisor. You cannot download them there anyway why are you trying to put them there? The guest VM does not care where they are shared from. Just put them someplace accessible. or even download them directly in the guest VM.
I am not arguing best hypervisor platform. I am simply stating you are doing things wrong and causing your own problems.
I'm guessing that he might be saying that he has no NAS, and doesn't want to create a share from his desktop machine to make those ISOs available to the hypervisor.
ESXi allows you to have a folder on the DataStore that you can then reference. I did this for my ESXi server. Same goes for my XS, I had a local piece of storage on the hypervisor for ISOs.
I don't see an actual issue with this. The biggest one I seem is that you might be using more expensive disk to store ISOs instead of storing them on a NAS.
And Hyper-V lets you access share a folder too. It is all windows, so the admin share is there and active.
\\hypervservername\c$\somefolder